Skip to main content

Mac Non-Functional Sensor (Due to MDM)

Summary: Due to the nature of MacOS devices, the MDM profile should be deployed before the sensor is installed to be able to communicate with the console.

Question_md: A macOS device has the Cyberhaven sensor installed, but the sensor is non-functional

Answer_md: If the MDM profile is not deployed before the Cyberhaven sensor , the sensor doesn 't receive the necessary backend configuration, and will remain inactive or non-functional after install.

Symptoms:

  • Sensor is installed, MDM appears applied but sensor is inactive. Usually due to installing sensor first and then deploying MDM
  • Logs show persistent warnings about MDM or backend configuration

  1. From the Cyberhaven logs - Open CyberhavenAutoUpdater.log and look for MDM related errors.
    [Managed.loadLocalOrFetchRemoteSettings():77] WARNING: No valid Backend URL was found. Waiting until set either manually or by MDM profile...

  2. Following lines will look like below which indicates the sensor is still operating as if no MDM profile is present or it's improperly configured.
    [MDM.log():246] WARNING: Manual install or MDM profile removed

  3. Next we should open and analyze io.cyberhaven.lightbeam.plist in the managed-prefernces folder from the diag. Open the file from Finder and compare a valid plist vs invalid. Expand the items if applicable, the plist should only have the backend url and token if the MDM profile was properly deployed

To Resolve:

  1. Remove the existing Cyberhaven profile

  2. Upload the correct.mobileconfig profile

    • Go to your MDM platform's configuration profile section.

    • Do not manually create or modify a profile.

    • Instead, use the upload option provided by your MDM (e.g., Jamf, Intune, Kandji, etc.).

    • Upload the .mobileconfig file downloaded directly from the Cyberhaven Console.

  3. Assign the new profile to the appropriate devices

    • Name it clearly (e.g., Cyberhaven Sensor Profile)

    • Scope or assign it to the target macOS devices

    • Confirm that the profile is successfully deployed and installed

  4. Reinstall the sensor or just restart the sensor and should be able to pick up the proper MDM and the error in UI will clear out